AutoRank Pro v2.0.4 Installation Manual[ Installation ] | [ HTML Template Feature ] | [ Templates ] | [ Cron Help ] | [ Tech Support ]Installation Procedure
Open all of the files that have a .cgi extension in a text editor. You will need to set the location of Perl 5 on your server. This is done on the first line of the file: #!/usr/bin/perl Change the /usr/bin/perl value to match your system's setup. If you have telnet access you can locate perl by typing the following command: which perl In most cases, /usr/bin/perl or /usr/local/bin/perl is a valid setting. Note that this must point to Perl 5. Ask your server administrator if you are unsure about the perl location. Login to your FTP server, and change into the directory where you will be installing the CGI scripts. (We recommend that this directory be inside a cgi-bin or equivalent directory) In that directory, create 3 more directories. Name them data, sdata, and templates. These directories will contain all of the files that control script operation. The HTML files that the script creates (the files that contain the list) will need to be in a seperate directory located outside of the cgi-bin. Open the files rankem.cgi, functions.cgi, and out.cgi in a text editor. You will now need to set the one variable - $FUNCTIONS::SCRIPT_DATA_DIR - in each of these files. That variable needs to be set to the full Unix path to the sdata directory that you just created. Once you have set that variable in all three of those files, save them. Note that you should not put a / at the end of the directory path! Now, upload all of the .cgi files to the directory that you want them installed in. Make sure that you are uploading in ASCII mode. Next, upload the errors.dat and admin.dat files to the sdata directory that you created - again in ASCII mode. Finally, upload all of the .htmlt files to the templates directory that you created - in ASCII mode. You will now need to set permissions on the files you uploaded, and directories that you created. Below you will see a table with recommended permissions settings. These settings should work for most servers, however others may require different settings.
Example Directory Structure /home/username/cgi-bin/autorank location of .cgi files /home/username/cgi-bin/autorank/sdata location of script data files (admin.dat, errors.dat) /home/username/cgi-bin/autorank/data location of member data files (created by script) /home/username/cgi-bin/autorank/templates location of all template files /home/username/public_html/toplist where the list HTML files will be written You are now ready to begin the WWW based portion of the setup. In your browser, type in the full URL to the setup.cgi file on your server. This will bring up the portion of the script where you will set all of the variables. Details and examples for each variable are given, so follow along through that to get all of the variables set properly. After you have set all of the variables, enter the default password admin and click the button. If everything went well, you will be presented with a page telling you that the variables have been recorded. To do further verification of your settings you can call the setup.cgi script like setup.cgi?verify. This will preform a series of tests and report the results. You should now be ready to begin using the scripts. The first thing you will want to do is point your browser to admin.cgi. Login using the default password admin - make sure you press the login button with your mouse pointer and not simply hit enter on your keyboard. Once inside the admin script you can start exploring the features, but make sure that you change your administrative password soon after your initial installation. Before re-ranking the list you must setup table properties or an HTML template from the second pulldown menu. Failure to do so will result in an error being reported. To get descriptions of the administrative functions, you can view the admin_f.html file included with the distribution. This file details what each of the functions do. Other Installation Notes
This feature is implemented in v2.0.4, however it is still in development stages. We will not be adding documentation until it is complete, so if you want to edit the template files you will be doing so at your own risk!
|